Technologies for switching network traffic in a data center

ABSTRACT

Technologies for switching network traffic include a network switch. The network switch includes one or more processors and communication circuitry coupled to the one or more processors. The communication circuitry is capable of switching network traffic of multiple link layer protocols. Additionally, the network switch includes one or more memory devices storing instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded, and determine a link layer protocol of the received network traffic. The instructions additionally cause the network switch to forward the network traffic as a function of the determined link layer protocol. Other embodiments are also described and claimed.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/395,203, filed Dec. 30, 2016, which in turn claims thebenefit of U.S. Provisional Patent Application No. 62/365,969, filedJul. 22, 2016, U.S. Provisional Patent Application No. 62/376,859, filedAug. 18, 2016, and U.S. Provisional Patent Application No. 62/427,268,filed Nov. 29, 2016.

BACKGROUND

In a typical data center that provides computing services, such as cloudservices, multiple compute devices may be assigned workloads to providethe requested services for a client. Given the latency and bandwidthlimitations of twisted-pair copper cabling and the correspondingnetworking components (e.g., switches) in such data centers, thephysical hardware resources, including processors, volatile andnon-volatile memory, accelerator devices (e.g., co-processors, fieldprogrammable gate arrays (FPGA), digital signal processors (DSPs),application specific integrated circuits (ASICs), etc.), and datastorage devices, that may be utilized to perform any given workload aretypically included locally in each compute device, rather than beingdispersed throughout the data center. As such, depending on the types ofworkloads assigned (e.g., processor intensive but light on memory use,memory intensive but light on processor use, etc.), a data center mayinclude many unused physical hardware resources and yet be unable totake on additional work without overloading the compute devices.

Furthermore, some typical data centers are designed to operate as a highperformance computing (HPC) cluster, using a specialized networkingprotocol (e.g., Intel OmniPath) to coordinate the communication andprocessing of workloads, while other data centers are designed tocommunicate using other communication protocols, such as Ethernet. Thenetworking components in typical data centers are not equipped to manageboth HPC network traffic and other types of network traffic, therebylimiting their usefulness to specific workload types.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a diagram of a conceptual overview of a data center in whichone or more techniques described herein may be implemented according tovarious embodiments;

FIG. 2 is a diagram of an example embodiment of a logical configurationof a rack of the data center of FIG. 1;

FIG. 3 is a diagram of an example embodiment of another data center inwhich one or more techniques described herein may be implementedaccording to various embodiments;

FIG. 4 is a diagram of another example embodiment of a data center inwhich one or more techniques described herein may be implementedaccording to various embodiments;

FIG. 5 is a diagram of a connectivity scheme representative oflink-layer connectivity that may be established among various sleds ofthe data centers of FIGS. 1, 3, and 4;

FIG. 6 is a diagram of a rack architecture that may be representative ofan architecture of any particular one of the racks depicted in FIGS. 1-4according to some embodiments;

FIG. 7 is a diagram of an example embodiment of a sled that may be usedwith the rack architecture of FIG. 6;

FIG. 8 is a diagram of an example embodiment of a rack architecture toprovide support for sleds featuring expansion capabilities;

FIG. 9 is a diagram of an example embodiment of a rack implementedaccording to the rack architecture of FIG. 8;

FIG. 10 is a diagram of an example embodiment of a sled designed for usein conjunction with the rack of FIG. 9;

FIG. 11 is a diagram of an example embodiment of a data center in whichone or more techniques described herein may be implemented according tovarious embodiments;

FIG. 12 is a simplified block diagram of at least one embodiment of aswitch used in the connectivity scheme of FIG. 5;

FIG. 13 is a simplified block diagram of at least one embodiment of anenvironment that may be established by the switch of FIGS. 5 and 12; and

FIGS. 14-15 are a simplified flow diagram of at least one embodiment ofa method for switching network traffic that may be performed by theswitch of FIGS. 5,12, and 13.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described. Additionally, it should be appreciated that itemsincluded in a list in the form of “at least one A, B, and C” can mean(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).Similarly, items listed in the form of “at least one of A, B, or C” canmean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon a transitory or non-transitory machine-readable (e.g.,computer-readable) storage medium, which may be read and executed by oneor more processors. A machine-readable storage medium may be embodied asany storage device, mechanism, or other physical structure for storingor transmitting information in a form readable by a machine (e.g., avolatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

FIG. 1 illustrates a conceptual overview of a data center 100 that maygenerally be representative of a data center or other type of computingnetwork in/for which one or more techniques described herein may beimplemented according to various embodiments. As shown in FIG. 1, datacenter 100 may generally contain a plurality of racks, each of which mayhouse computing equipment comprising a respective set of physicalresources. In the particular non-limiting example depicted in FIG. 1,data center 100 contains four racks 102A to 102D, which house computingequipment comprising respective sets of physical resources (PCRs) 105Ato 105D. According to this example, a collective set of physicalresources 106 of data center 100 includes the various sets of physicalresources 105A to 105D that are distributed among racks 102A to 102D.Physical resources 106 may include resources of multiple types, suchas—for example—processors, co-processors, accelerators,field-programmable gate arrays (FPGAs), memory, and storage. Theembodiments are not limited to these examples.

The illustrative data center 100 differs from typical data centers inmany ways. For example, in the illustrative embodiment, the circuitboards (“sleds”) on which components such as CPUs, memory, and othercomponents are placed are designed for increased thermal performance. Inparticular, in the illustrative embodiment, the sleds are shallower thantypical boards. In other words, the sleds are shorter from the front tothe back, where cooling fans are located. This decreases the length ofthe path that air must to travel across the components on the board.Further, the components on the sled are spaced further apart than intypical circuit boards, and the components are arranged to reduce oreliminate shadowing (i.e., one component in the air flow path of anothercomponent). In the illustrative embodiment, processing components suchas the processors are located on a top side of a sled while near memory,such as dual in-line memory modules (DIMMs) or other memory modules orstacks, are located on a bottom side of the sled. As a result of theenhanced airflow provided by this design, the components may operate athigher frequencies and power levels than in typical systems, therebyincreasing performance. Furthermore, the sleds are configured to blindlymate with power and data communication interfaces (e.g., cables, busbars, optical interfaces, etc.) in each rack 102A, 102B, 102C, 102D,enhancing their ability to be quickly removed, upgraded, reinstalled,and/or replaced. Similarly, individual components located on the sleds,such as processors, accelerators, memory, and data storage drives, areconfigured to be easily upgraded due to their increased spacing fromeach other. In the illustrative embodiment, the components additionallyinclude hardware attestation features to prove their authenticity.

Furthermore, in the illustrative embodiment, the data center 100utilizes a single network architecture (“fabric”) that supports multipleother network architectures including Ethernet and Omni-Path. The sleds,in the illustrative embodiment, are coupled to switches via opticalfibers, which provide higher bandwidth and lower latency than typicaltwisted pair cabling (e.g., Category 5, Category 5e, Category 6, etc.).Due to the high bandwidth, low latency interconnections and networkarchitecture, the data center 100 may, in use, pool resources, such asmemory, accelerators (e.g., graphics accelerators, FPGAs, applicationspecific integrated circuits (ASICs), etc.), and data storage drivesthat are physically disaggregated, and provide them to compute resources(e.g., processors) on an as needed basis, enabling the compute resourcesto access the pooled resources as if they were local. The illustrativedata center 100 additionally receives usage information for the variousresources, predicts resource usage for different types of workloadsbased on past resource usage, and dynamically reallocates the resourcesbased on this information.

The racks 102A, 102B, 102C, 102D of the data center 100 may includephysical design features that facilitate the automation of a variety oftypes of maintenance tasks. For example, data center 100 may beimplemented using racks that are designed to be robotically-accessed,and to accept and house robotically-manipulatable resource sleds.Furthermore, in the illustrative embodiment, the racks 102A, 102B, 102C,102D include integrated power sources that receive a greater voltagethan is typical for power sources. The increased voltage enables thepower sources to provide additional power to the components on eachsled, enabling the components to operate at higher than typicalfrequencies. In the illustrative embodiment, the power sources include277 VAC inputs to power supply units (PSUs), to reduce the inputcurrent, and reduce the losses that may occur if higher input currentswere used to compensate for lower input voltages. Additionally, in theillustrative embodiment, more current input is provided to each sled toallow each sled to reach higher power operating points.

FIG. 2 illustrates an exemplary logical configuration of a rack 202 ofthe data center 100. As shown in FIG. 2, rack 202 may generally house aplurality of sleds, each of which may comprise a respective set ofphysical resources. In the particular non-limiting example depicted inFIG. 2, rack 202 houses sleds 204-1 to 204-4 comprising respective setsof physical resources 205-1 to 205-4, each of which constitutes aportion of the collective set of physical resources 206 comprised inrack 202. With respect to FIG. 1, if rack 202 is representative of—forexample—rack 102A, then physical resources 206 may correspond to thephysical resources 105A comprised in rack 102A. In the context of thisexample, physical resources 105A may thus be made up of the respectivesets of physical resources, including physical storage resources 205-1,physical accelerator resources 205-2, physical memory resources 204-3,and physical compute resources 205-5 comprised in the sleds 204-1 to204-4 of rack 202. The embodiments are not limited to this example. Eachsled may contain a pool of each of the various types of physicalresources (e.g., compute, memory, accelerator, storage). By havingrobotically accessible and robotically manipulatable sleds comprisingdisaggregated resources, each type of resource can be upgradedindependently of each other and at their own optimized refresh rate. Inthe illustrative embodiment, “robotically accessible” and “roboticallymanipulatable” means easily accessible and easily manipulatable, suchthat a robot or human could complete the operation.

FIG. 3 illustrates an example of a data center 300 that may generally berepresentative of one in/for which one or more techniques describedherein may be implemented according to various embodiments. In theparticular non-limiting example depicted in FIG. 3, data center 300comprises racks 302-1 to 302-32. In various embodiments, the racks ofdata center 300 may be arranged in such fashion as to define and/oraccommodate various access pathways. For example, as shown in FIG. 3,the racks of data center 300 may be arranged in such fashion as todefine and/or accommodate access pathways 311A, 311B, 311C, and 311D. Insome embodiments, the presence of such access pathways may generallyenable automated maintenance equipment, such as robotic maintenanceequipment, to physically access the computing equipment housed in thevarious racks of data center 300 and perform automated maintenance tasks(e.g., replace a failed sled, upgrade a sled). In various embodiments,the dimensions of access pathways 311A, 311B, 311C, and 311D, thedimensions of racks 302-1 to 302-32, and/or one or more other aspects ofthe physical layout of data center 300 may be selected to facilitatesuch automated operations. The embodiments are not limited in thiscontext.

FIG. 4 illustrates an example of a data center 400 that may generally berepresentative of one in/for which one or more techniques describedherein may be implemented according to various embodiments. As shown inFIG. 4, data center 400 may feature an optical fabric 412. Opticalfabric 412 may generally comprise a combination of optical signalingmedia (such as optical cabling, also referred to herein as optical fiberor fiber bundles) and optical switching infrastructure, including one ormore switches 515 (also referred to herein as network switches) that maybe included in a central location 406, via which any particular sled indata center 400 can send signals to (and receive signals from) each ofthe other sleds in data center 400. The signaling connectivity thatoptical fabric 412 provides to any given sled may include connectivityboth to other sleds in a same rack and sleds in other racks. In theparticular non-limiting example depicted in FIG. 4, data center 400includes four racks 402A to 402D. Racks 402A to 402D house respectivepairs of sleds 404A-1 and 404A-2, 404B-1 and 404B-2, 404C-1 and 404C-2,and 404D-1 and 404D-2. Thus, in this example, data center 400 comprisesa total of eight sleds. Via optical fabric 412, each such sled maypossess signaling connectivity with each of the seven other sleds indata center 400. For example, via optical fabric 412, sled 404A-1 inrack 402A may possess signaling connectivity with sled 404A-2 in rack402A, as well as the six other sleds 404B-1, 404B-2, 404C-1, 404C-2,404D-1, and 404D-2 that are distributed among the other racks 402B,402C, and 402D of data center 400. The embodiments are not limited tothis example.

FIG. 5 illustrates an overview of a connectivity scheme 500 that maygenerally be representative of link-layer connectivity that may beestablished in some embodiments among the various sleds of a datacenter, such as any of example data centers 100, 300, and 400 of FIGS.1, 3, and 4. Connectivity scheme 500 may be implemented using an opticalfabric that features a multi-mode optical switching infrastructure 514.Multi-mode optical switching infrastructure 514 may generally comprise aswitching infrastructure that is capable of receiving communicationsaccording to multiple link-layer protocols via a same unified set ofoptical signaling media, and properly switching such communications. Invarious embodiments, multi-mode optical switching infrastructure 514 maybe implemented using one or more multi-mode optical switches 515. Invarious embodiments, multi-mode optical switches 515 may generallycomprise high-radix switches. In some embodiments, multi-mode opticalswitches 515 may comprise multi-ply switches, such as four-ply switches.In various embodiments, multi-mode optical switches 515 may featureintegrated silicon photonics that enable them to switch communicationswith significantly reduced latency in comparison to conventionalswitching devices. In some embodiments, multi-mode optical switches 515may constitute leaf switches 530 in a leaf-spine architectureadditionally including one or more multi-mode optical spine switches520.

In various embodiments, multi-mode optical switches 515 may be capableof receiving both Ethernet protocol communications carrying InternetProtocol (IP packets) and communications according to a second,high-performance computing (HPC) link-layer protocol (e.g., Intel'sOmni-Path Architecture's, InfiniBand) via optical signaling media of anoptical fabric. Other native protocols may be included, such as rawacceleration intercommunication protocols, storage protocols, or evenapplication-specific protocols that are not embedded or tunneled withinexisting IP or OmniPath fabric protocols. As reflected in FIG. 5, withrespect to any particular pair of sleds 504A and 504B possessing opticalsignaling connectivity to the optical fabric, connectivity scheme 500may thus provide support for link-layer connectivity via both Ethernetlinks and HPC links. Thus, both Ethernet and HPC communications can besupported by a single high-bandwidth, low-latency switch fabric. Theembodiments are not limited to this example. In some embodiments, theswitches 515 are in a central location (e.g., the central location 406)in the data center 100 rather than being located within the racks,thereby enabling the switches 515 to be easily accessed by a human.Furthermore, each sled 504 may be coupled to four switches 515 that eachprovides one quarter of a total bandwidth, such as a 50 gigabits persecond upstream fiber optic connection and a 50 gigabits per seconddownstream fiber optic connection of a total bandwidth of 200 gigabitsper second upstream and 200 gigabits per second downstream. In otherembodiments, the total bandwidth may be a different amount than 200gigabits per second upstream and 200 gigabits per second downstream. Forexample, in other embodiments, each optical fiber may provide greaterthan 50 gigabits per second upstream and 50 gigabits per seconddownstream. As a result, each sled 504 may receive a total upstreambandwidth of 200 gigabits per second and a total downstream bandwidth of200 gigabits per second. By spreading the bandwidth among multipleswitches 515, if any one switch 515 becomes inoperative, the other threefourths of the bandwidth (e.g., 150 gigabits) remains available. Assuch, the connectivity scheme in such embodiments is more failuretolerant than embodiments in which all of the available bandwidth isconsolidated in a single switch.

FIG. 6 illustrates a general overview of a rack architecture 600 thatmay be representative of an architecture of any particular one of theracks depicted in FIGS. 1 to 4 according to some embodiments. Asreflected in FIG. 6, rack architecture 600 may generally feature aplurality of sled spaces into which sleds may be inserted, each of whichmay be robotically or humanly accessible via a rack access region 601.In the particular non-limiting example depicted in FIG. 6, rackarchitecture 600 features five sled spaces 603-1 to 603-5. Sled spaces603-1 to 603-5 feature respective multi-purpose connector modules(MPCMs) 616-1 to 616-5. When a sled is inserted into any given one ofsled spaces 603-1 to 603-5, the corresponding MPCM (e.g., MPCM 616-3)may couple with a counterpart MPCM of the inserted sled. This couplingmay provide the inserted sled with connectivity to both signalinginfrastructure and power infrastructure of the rack in which it ishoused. Included among the types of sleds to be accommodated by rackarchitecture 600 may be one or more types of sleds that featureexpansion capabilities.

FIG. 7 illustrates an example of a sled 704 that may be representativeof a sled of such a type. As shown in FIG. 7, sled 704 may comprise aset of physical resources 705, as well as an MPCM 716 designed to couplewith a counterpart MPCM when sled 704 is inserted into a sled space suchas any of sled spaces 603-1 to 603-5 of FIG. 6. Sled 704 may alsofeature an expansion connector 717. Expansion connector 717 maygenerally comprise a socket, slot, or other type of connection elementthat is capable of accepting one or more types of expansion modules,such as an expansion sled 718. By coupling with a counterpart connectoron expansion sled 718, expansion connector 717 may provide physicalresources 705 with access to supplemental computing resources 705Bresiding on expansion sled 718. The embodiments are not limited in thiscontext.

FIG. 8 illustrates an example of a rack architecture 800 that may berepresentative of a rack architecture that may be implemented in orderto provide support for sleds featuring expansion capabilities, such assled 704 of FIG. 7. In the particular non-limiting example depicted inFIG. 8, rack architecture 800 includes seven sled spaces 803-1 to 803-7,which feature respective MPCMs 816-1 to 816-7. Sled spaces 803-1 to803-7 include respective primary regions 803-1A to 803-7A and respectiveexpansion regions 803-1B to 803-7B. With respect to each such sledspace, when the corresponding MPCM is coupled with a counterpart MPCM ofan inserted sled, the primary region may generally constitute a regionof the sled space that physically accommodates the inserted sled. Theexpansion region may generally constitute a region of the sled spacethat can physically accommodate an expansion module, such as expansionsled 718 of FIG. 7, in the event that the inserted sled is configuredwith such a module.

FIG. 9 illustrates an example of a rack 902 that may be representativeof a rack implemented according to rack architecture 800 of FIG. 8according to some embodiments. In the particular non-limiting exampledepicted in FIG. 9, rack 902 features seven sled spaces 903-1 to 903-7,which include respective primary regions 903-1A to 903-7A and respectiveexpansion regions 903-1B to 903-7B. In various embodiments, temperaturecontrol in rack 902 may be implemented using an air cooling system. Forexample, as reflected in FIG. 9, rack 902 may feature a plurality offans 919 that are generally arranged to provide air cooling within thevarious sled spaces 903-1 to 903-7. In some embodiments, the height ofthe sled space is greater than the conventional “1U” server height. Insuch embodiments, fans 919 may generally comprise relatively slow, largediameter cooling fans as compared to fans used in conventional rackconfigurations. Running larger diameter cooling fans at lower speeds mayincrease fan lifetime relative to smaller diameter cooling fans runningat higher speeds while still providing the same amount of cooling. Thesleds are physically shallower than conventional rack dimensions.Further, components are arranged on each sled to reduce thermalshadowing (i.e., not arranged serially in the direction of air flow). Asa result, the wider, shallower sleds allow for an increase in deviceperformance because the devices can be operated at a higher thermalenvelope (e.g., 250 W) due to improved cooling (i.e., no thermalshadowing, more space between devices, more room for larger heat sinks,etc.).

MPCMs 916-1 to 916-7 may be configured to provide inserted sleds withaccess to power sourced by respective power modules 920-1 to 920-7, eachof which may draw power from an external power source 921. In variousembodiments, external power source 921 may deliver alternating current(AC) power to rack 902, and power modules 920-1 to 920-7 may beconfigured to convert such AC power to direct current (DC) power to besourced to inserted sleds. In some embodiments, for example, powermodules 920-1 to 920-7 may be configured to convert 277-volt AC powerinto 12-volt DC power for provision to inserted sleds via respectiveMPCMs 916-1 to 916-7. The embodiments are not limited to this example.

MPCMs 916-1 to 916-7 may also be arranged to provide inserted sleds withoptical signaling connectivity to a multi-mode optical switchinginfrastructure 914, which may be the same as—or similar to—multi-modeoptical switching infrastructure 514 of FIG. 5. In various embodiments,optical connectors contained in MPCMs 916-1 to 916-7 may be designed tocouple with counterpart optical connectors contained in MPCMs ofinserted sleds to provide such sleds with optical signaling connectivityto multi-mode optical switching infrastructure 914 via respectivelengths of optical cabling 922-1 to 922-7, also referred to herein asoptical fiber. In some embodiments, each such length of optical cablingmay extend from its corresponding MPCM to an optical interconnect loom923 that is external to the sled spaces of rack 902. In variousembodiments, optical interconnect loom 923 may be arranged to passthrough a support post or other type of load-bearing element of rack902. The embodiments are not limited in this context. Because insertedsleds connect to an optical switching infrastructure via MPCMs, theresources typically spent in manually configuring the rack cabling toaccommodate a newly inserted sled can be saved.

FIG. 10 illustrates an example of a sled 1004 that may be representativeof a sled designed for use in conjunction with rack 902 of FIG. 9according to some embodiments. Sled 1004 may feature an MPCM 1016 thatcomprises an optical connector 1016A and a power connector 1016B, andthat is designed to couple with a counterpart MPCM of a sled space inconjunction with insertion of MPCM 1016 into that sled space. CouplingMPCM 1016 with such a counterpart MPCM may cause power connector 1016 tocouple with a power connector comprised in the counterpart MPCM. Thismay generally enable physical resources 1005 of sled 1004 to sourcepower from an external source, via power connector 1016 and powertransmission media 1024 that conductively couples power connector 1016to physical resources 1005.

Sled 1004 may also include multi-mode optical network interfacecircuitry 1026. Multi-mode optical network interface circuitry 1026 maygenerally comprise circuitry that is capable of communicating overoptical signaling media according to each of multiple link-layerprotocols supported by multi-mode optical switching infrastructure 914of FIG. 9. In some embodiments, multi-mode optical network interfacecircuitry 1026 may be capable both of Ethernet protocol communicationsand of communications according to a second, high-performance protocol.In various embodiments, multi-mode optical network interface circuitry1026 may include one or more optical transceiver modules 1027, each ofwhich may be capable of transmitting and receiving optical signals overeach of one or more optical channels. The embodiments are not limited inthis context.

Coupling MPCM 1016 with a counterpart MPCM of a sled space in a givenrack may cause optical connector 1016A to couple with an opticalconnector comprised in the counterpart MPCM. This may generallyestablish optical connectivity between optical cabling of the sled andmulti-mode optical network interface circuitry 1026, via each of a setof optical channels 1025. Multi-mode optical network interface circuitry1026 may communicate with the physical resources 1005 of sled 1004 viaelectrical signaling media 1028. In addition to the dimensions of thesleds and arrangement of components on the sleds to provide improvedcooling and enable operation at a relatively higher thermal envelope(e.g., 250 W), as described above with reference to FIG. 9, in someembodiments, a sled may include one or more additional features tofacilitate air cooling, such as a heat pipe and/or heat sinks arrangedto dissipate heat generated by physical resources 1005. It is worthy ofnote that although the example sled 1004 depicted in FIG. 10 does notfeature an expansion connector, any given sled that features the designelements of sled 1004 may also feature an expansion connector accordingto some embodiments. The embodiments are not limited in this context.

FIG. 11 illustrates an example of a data center 1100 that may generallybe representative of one in/for which one or more techniques describedherein may be implemented according to various embodiments. As reflectedin FIG. 11, a physical infrastructure management framework 1150A may beimplemented to facilitate management of a physical infrastructure 1100Aof data center 1100. In various embodiments, one function of physicalinfrastructure management framework 1150A may be to manage automatedmaintenance functions within data center 1100, such as the use ofrobotic maintenance equipment to service computing equipment withinphysical infrastructure 1100A. In some embodiments, physicalinfrastructure 1100A may feature an advanced telemetry system thatperforms telemetry reporting that is sufficiently robust to supportremote automated management of physical infrastructure 1100A. In variousembodiments, telemetry information provided by such an advancedtelemetry system may support features such as failureprediction/prevention capabilities and capacity planning capabilities.In some embodiments, physical infrastructure management framework 1150Amay also be configured to manage authentication of physicalinfrastructure components using hardware attestation techniques. Forexample, robots may verify the authenticity of components beforeinstallation by analyzing information collected from a radio frequencyidentification (RFID) or other physical tag associated with eachcomponent to be installed. The embodiments are not limited in thiscontext.

As shown in FIG. 11, the physical infrastructure 100A of data center1100 may comprise an optical fabric 1112, which may include a multi-modeoptical switching infrastructure 1114. Optical fabric 1112 andmulti-mode optical switching infrastructure 1114 may be the same as—orsimilar to—optical fabric 412 of FIG. 4 and multi-mode optical switchinginfrastructure 514 of FIG. 5, respectively, and may providehigh-bandwidth, low-latency, multi-protocol connectivity among sleds ofdata center 1100. As discussed above, with reference to FIG. 1, invarious embodiments, the availability of such connectivity may make itfeasible to disaggregate and dynamically pool resources such asaccelerators, memory, and storage. In some embodiments, for example, oneor more pooled accelerator sleds 1130 may be included among the physicalinfrastructure 1100A of data center 1100, each of which may comprise apool of accelerator resources—such as co-processors, specialtyprocessors, and/or FPGAs, for example—that is globally accessible toother sleds via optical fabric 1112 and multi-mode optical switchinginfrastructure 1114.

In another example, in various embodiments, one or more pooled storagesleds 1132 may be included among the physical infrastructure 1100A ofdata center 1100, each of which may comprise a pool of storage resourcesthat is available globally accessible to other sleds via optical fabric1112 and multi-mode optical switching infrastructure 1114. In someembodiments, such pooled storage sleds 1132 may comprise pools ofsolid-state storage devices such as solid-state drives (SSDs). Invarious embodiments, one or more high-performance processing sleds 1134may be included among the physical infrastructure 1100A of data center1100. In some embodiments, high-performance processing sleds 1134 maycomprise pools of high-performance processors, as well as coolingfeatures that enhance air cooling to yield a higher thermal envelope ofup to 250 W or more. In various embodiments, any given high-performanceprocessing sled 1134 may feature an expansion connector 1117 that canaccept a far memory expansion sled, such that the far memory that islocally available to that high-performance processing sled 1134 isdisaggregated from the processors and near memory comprised on thatsled. In some embodiments, such a high-performance processing sled 1134may be configured with far memory using an expansion sled that compriseslow-latency SSD storage. The optical infrastructure allows for computeresources on one sled to utilize remote accelerator/FPGA, memory, and/orSSD resources that are disaggregated on a sled located on the same rackor any other rack in the data center. The remote resources can belocated in the spine-leaf network architecture described above withreference to FIG. 5. The embodiments are not limited in this context.

In various embodiments, one or more layers of abstraction may be appliedto the physical resources of physical infrastructure 1100A in order todefine a virtual infrastructure, such as a software-definedinfrastructure 1100B. In some embodiments, virtual computing resources1136 of software-defined infrastructure 1100B may be allocated tosupport the provision of cloud services 1140. In various embodiments,particular sets of virtual computing resources 1136 may be grouped forprovision to cloud services 1140 in the form of SDI services 1138.Examples of cloud services 1140 may include—without limitation—softwareas a service (SaaS) services 1142, platform as a service (PaaS) services1144, and infrastructure as a service (IaaS) services 1146.

In some embodiments, management of software-defined infrastructure (SDI)1100B may be conducted using a virtual infrastructure managementframework 1150B. In various embodiments, virtual infrastructuremanagement framework 1150B may be designed to implement workloadfingerprinting techniques and/or machine-learning techniques inconjunction with managing allocation of virtual computing resources 1136and/or SDI services 1138 to cloud services 1140. In some embodiments,virtual infrastructure management framework 1150B may use/consulttelemetry data in conjunction with performing such resource allocation.In various embodiments, an application/service management framework1150C may be implemented in order to provide QoS management capabilitiesfor cloud services 1140. The embodiments are not limited in thiscontext.

Referring now to FIG. 12, the switch 515, in the illustrativeembodiment, is a multi-mode optical switch that connects with sleds(e.g., sleds 704, 1004) through an optical connection (e.g., the opticalfabric 1112) to provide higher bandwidth and lower latency than switchesthat connect with compute devices using typical twisted pair cabling(e.g., Category 5, Category 5e, Category 6, etc.). The higher bandwidthand lower latency interconnections enable the pooling of resources, suchas memory, accelerators (e.g., graphics accelerators, FPGAs, ASICs,etc.), and data storage devices that are physically disaggregated, foruse by compute resources (e.g., processors) to execute workloads on anas needed basis. More specifically, the high bandwidth and low latencyprovided by the optical connections and the corresponding switches 515enable the physical resources 206 (shown in FIG. 2) located in variousplaces in the data center 100, 300, 400 to provide similarresponsiveness as if they were local to the processor making use ofthem. Furthermore, in the illustrative embodiment, the switch 515 ismulti-mode, meaning it is capable of switching (i.e., forwarding)network traffic formatted according to two or more different link layerprotocols, such as an HPC link layer protocol (e.g., Intel OmniPath),Ethernet, or any other specialized communications protocol such as rawaccelerator intercommunication protocols, storage protocols, or evenapplication-specific protocols that are not embedded/tunneled withinexisting Internet Protocol (IP) or OmniPath protocols.

Still referring to FIG. 12, the switch 515 may be embodied as any typeof device capable of performing the functions described herein,including receiving network traffic from one or more devices through anoptical connection, determining a communication protocol of the networktraffic, determining the destination device for the network trafficusing the communication protocol, and forwarding the network traffic tothe destination device through another optical connection. For example,the switch 515 may be embodied as a computer, a multiprocessor system,or a network appliance (e.g., physical or virtual). As shown in FIG. 12,the illustrative switch 515 includes a central processing unit (CPU)1202, a main memory 1204, an input/output (I/O) subsystem 1206,communication circuitry 1208, and one or more data storage devices 1212.Of course, in other embodiments, the switch 515 may include other oradditional components, such as those commonly found in a computer (e.g.,display, peripheral devices, etc.). Additionally, in some embodiments,one or more of the illustrative components may be incorporated in, orotherwise form a portion of, another component. For example, in someembodiments, the main memory 1204, or portions thereof, may beincorporated in the CPU 1202.

The CPU 1202 may be embodied as any type of processor capable ofperforming the functions described herein. The CPU 1202 may be embodiedas a single or multi-core processor(s), a microcontroller, or otherprocessor or processing/controlling circuit. In some embodiments, theCPU 1202 may be embodied as, include, or be coupled to a fieldprogrammable gate array (FPGA), an application specific integratedcircuit (ASIC), reconfigurable hardware or hardware circuitry, or otherspecialized hardware to facilitate performance of the functionsdescribed herein. Similarly, the main memory 1204 may be embodied as anytype of volatile (e.g., dynamic random access memory (DRAM), etc.) ornon-volatile memory or data storage capable of performing the functionsdescribed herein. In some embodiments, all or a portion of the mainmemory 1204 may be integrated into the CPU 1202. In operation, the mainmemory 1204 may store various software and data used during operationsuch as network traffic data, protocol data, address data, operatingsystems, applications, programs, libraries, and drivers.

The I/O subsystem 1206 may be embodied as circuitry and/or components tofacilitate input/output operations with the CPU 1202, the main memory1204, and other components of the switch 515. For example, the I/Osubsystem 1206 may be embodied as, or otherwise include, memorycontroller hubs, input/output control hubs, integrated sensor hubs,firmware devices, communication links (e.g., silicon photonics,point-to-point links, bus links, wires, cables, light guides, printedcircuit board traces, etc.), and/or other components and subsystems tofacilitate the input/output operations. In some embodiments, the I/Osubsystem 1206 may form a portion of a system-on-a-chip (SoC) and beincorporated, along with one or more of the CPU 1202, the main memory1204, and other components of the switch 515, on a single integratedcircuit chip.

The communication circuitry 1208 may be embodied as any communicationcircuit, device, or collection thereof, capable of enablingcommunications over the network between the switch 515 and other devices(e.g., other switches 515 or sleds 704). In the illustrative embodiment,the communication circuitry 1208 includes components similar to themulti-mode optical network interface circuitry 1026 described above withreference to FIG. 10. The communication circuitry 1208 may be configuredto use multiple communication technologies (e.g., wired or wirelesscommunications) and associated protocols (e.g., Intel InfiniBand,Ethernet, Bluetooth, Wi-Fi, WiMAX, etc.) to effect such communication.In the illustrative embodiment, the communication circuitry 1208 isconfigured to communicate through the optical fabric 1112 described withreference to FIG. 11.

The illustrative communication circuitry 1208 includes one or more portlogics 1210. In the illustrative embodiment, each port logic 1210 may beembodied as an optical transceiver module 1027. Each port logic 1210 maybe embodied as one or more add-in-boards, daughtercards, networkinterface cards, controller chips, chipsets, or other devices that maybe used by the switch 515 to connect other devices (e.g., other switches515 and/or sleds 704) through a network (e.g., the multi-mode opticalswitching infrastructure 514, 914, 1114). In the illustrativeembodiment, the one or more port logics 1210 together enable concurrentcommunication with multiple other devices, (e.g., up to 1024 otherdevices). Further, in the illustrative embodiment, each device isconnected to the port logics 1210 with one optical fiber for incomingnetwork traffic (e.g., frames) and another optical fiber for outgoingnetwork traffic. In some embodiments, the port logics 1210 may beembodied as part of a system-on-a-chip (SoC) that includes one or moreprocessors, or included on a multichip package that also contains one ormore processors. In some embodiments, each port logic 1210 may include alocal processor (not shown) and/or a local memory (not shown) that areboth local to the port logic 1210. In such embodiments, the localprocessor of the port logic 1210 may be capable of performing one ormore of the functions of the CPU 1202 described herein. Additionally oralternatively, in such embodiments, the local memory of the port logic1210 may be integrated into one or more components of the switch 515 atthe board level, socket level, chip level, and/or other levels.

The one or more illustrative data storage devices 1212, may be embodiedas any type of devices configured for short-term or long-term storage ofdata such as, for example, memory devices and circuits, memory cards,hard disk drives, solid-state drives, or other data storage devices.Each data storage device 1212 may include a system partition that storesdata and firmware code for the data storage device 1212. Each datastorage device 1212 may also include an operating system partition thatstores data files and executables for an operating system.

Additionally, the switch 515 may include a display 1214. The display1214 may be embodied as, or otherwise use, any suitable displaytechnology including, for example, a liquid crystal display (LCD), alight emitting diode (LED) display, a cathode ray tube (CRT) display, aplasma display, and/or other display usable in a compute device. Thedisplay 1214 may include a touchscreen sensor that uses any suitabletouchscreen input technology to detect the user's tactile selection ofinformation displayed on the display including, but not limited to,resistive touchscreen sensors, capacitive touchscreen sensors, surfaceacoustic wave (SAW) touchscreen sensors, infrared touchscreen sensors,optical imaging touchscreen sensors, acoustic touchscreen sensors,and/or other type of touchscreen sensors.

Additionally or alternatively, the switch 515 may include one or moreperipheral devices 1216. Such peripheral devices 1216 may include anytype of peripheral device commonly found in a compute device such asspeakers, a mouse, a keyboard, and/or other input/output devices,interface devices, and/or other peripheral devices.

Referring now to FIG. 13, in the illustrative embodiment, the switch 515may establish an environment 1300 during operation. The illustrativeenvironment 1300 includes a network communicator 1320, a protocoldeterminer 1330, and a network traffic switcher 1340. Each of thecomponents of the environment 1300 may be embodied as hardware,firmware, software, or a combination thereof. As such, in someembodiments, one or more of the components of the environment 1300 maybe embodied as circuitry or a collection of electrical devices (e.g.,network communicator circuitry 1320, protocol determiner circuitry 1330,network traffic switcher circuitry 1340, etc.). It should be appreciatedthat, in such embodiments, one or more of the network communicatorcircuitry 1320, protocol determiner circuitry 1330, or network trafficswitcher circuitry 1340 may form a portion of one or more of the CPU1202, the main memory 1204, the I/O subsystem 1206, and/or othercomponents of the switch 515. The circuitry may be embodied as dedicatedhardware or general purpose processor(s) executing code to implementdesired functionality. In the illustrative embodiment, the environment1300 includes network traffic data 1302 which may be embodied as set ofdata (e.g., frames) received from a source device (e.g., another switch515 or physical resources 705 (e.g., a processor) residing on a sled704), targeted to another device (e.g., another switch 515 or physicalresources 705 (e.g., a processor) residing on a sled 704), and formattedpursuant to a corresponding communication protocol. Additionally, theillustrative environment 1300 includes protocol data 1304 indicative ofthe formats of various communication protocols (e.g., frame size,locations and sizes of fields within the frames, and/or one or morecodes typically embedded in frames of a particular communicationprotocol) and rules (e.g., locations within the frame to identify thedestination address, timing information on whether to forward the frameimmediately or to delay forwarding for a defined period of time, whetherand how to acknowledge receipt, etc.) for switching the network trafficpursuant to the corresponding protocol. Further, the illustrativeenvironment 1300 includes address data 1306 indicative of uniqueaddresses (e.g., media access control addresses) of devices (e.g.,physical resources 705 (e.g., a processor) residing on sleds 704 and/orswitches 515) connected to the present switch 515 and the correspondingphysical ports where the optical fiber associated with each of thedevices is connected.

In the illustrative environment 1300, the network communicator 1320,which may be embodied as hardware, firmware, software, virtualizedhardware, emulated architecture, and/or a combination thereof asdiscussed above, is configured to facilitate inbound and outboundnetwork communications (e.g., network traffic, network frames, networkpackets, network flows, etc.) to and from the switch 515, respectively.To do so, the network communicator 1320 is configured to receive andprocess network traffic (e.g., frames) from one device (e.g., anotherswitch 515 or a sled 704) and to forward the network traffic to anotherdevice (e.g., another switch 515 or a sled 704) using address dataencoded in the network traffic (e.g., in a frame header) in accordancewith the corresponding protocol of the network traffic (e.g., an HPCcommunication protocol, an Ethernet protocol, etc.). Accordingly, insome embodiments, at least a portion of the functionality of the networkcommunicator 1320 may be performed by the communication circuitry 1208,and, in the illustrative embodiment, by the one or more NICS 1210.

The protocol determiner 1330, which may be embodied as hardware,firmware, software, virtualized hardware, emulated architecture, and/ora combination thereof as discussed above, is configured to analyze areceived frame of the network traffic data 1302, identify a format ofthe frame, such as by identifying a size of the frame, fields within theframe such as a header and a payload, and/or identifying one or morecodes within the fields that are indicative of a particularcommunication protocol supported by the switch. In doing so, theprotocol determiner 1330 may be configured to compare the identifiedformat of the frame to the protocol data 1304 to identify a match andthe corresponding rules for switching the network traffic.

The network traffic switcher 1340, which may be embodied as hardware,firmware, software, virtualized hardware, emulated architecture, and/ora combination thereof as discussed above, is configured to identify theaddress of the device to which each frame of network traffic is to beforwarded, by extracting the data from the frame pursuant to theidentified network protocol (e.g., by extracting data from a particularlocation within the frame as specified in the protocol data), readingthe address data 1306 to match the identified address to a physical port(e.g., an optical channel 1025) of the NICS 1210 where the devicematching the identified address is connected to the switch 515, andissuing a request to the network communicator 1320 to transmit the frameof the network data through the physical port to the correspondingdevice.

Referring now to FIG. 14, in use, the switch 515 may execute a method1400 for switching network traffic. The method 1400 begins with block1402, in which the switch 515 determines whether to switch networktraffic. In the illustrative embodiment, the switch 515 determines toswitch network traffic if the switch 515 is powered on and connected tothe network (e.g., the multi-mode optical switching infrastructure 514,914, 1114). In other embodiments, the switch 515 may determine whetherto switch network traffic based on other factors. Regardless, inresponse to a determination to switch network traffic, in theillustrative embodiment, the method 1400 advances to block 1404 in whichthe switch 515 receives network traffic to be forwarded (i.e.,switched). The network traffic may be formatted pursuant to any ofmultiple supported link layer communication protocols, including a highperformance computing (HPC) protocol (e.g. Intel InfiniBand, etc.) oranother type of link layer communication protocol, such as Ethernet.

In receiving the network traffic, the switch 515 may receive networktraffic through an optical connection (e.g., optical fiber connected tothe communication circuitry 1208), as indicated in block 1406. Further,in the illustrative embodiment, in receiving the network traffic to thebe forwarded, the switch 515 receives the network traffic through aconnection having a portion (e.g., one quarter or other portion) of thetotal bandwidth of a link (e.g., a 50 gigabit per second connection of a200 gigabit per second link, a 100 gigabit per second connection of a400 gigabit per second link, a 200 gigabit per second connection of an800 gigabit per second link, etc.), as indicated in block 1408. Asdescribed herein, in the illustrative embodiment, the switch 515 is oneof multiple switches (e.g., four switches) in the data center 100 that,together, provide a total amount of gigabits per second connection forthe devices (e.g., the sleds 704) in the data center. In receiving thenetwork traffic, the switch 515 may receive the network traffic from asled 704, as indicated in block 1410. As an example, the network trafficreceived from the sled 704 may be the results from the execution of aworkload that was assigned to the sled 704 or may be instructions fromone sled 704 to another sled 704 to perform a particular operation(e.g., retrieve data, compress data, encrypt data, etc.) or the resultsof such an operation (e.g., retrieved data, compressed data, encrypteddata, etc.). As such, the switch 515 may receive the network trafficfrom a compute sled 704, such as a sled 704 that includes one or moreprocessors (e.g., physical compute resources 205-4), as indicated inblock 1412. Additionally or alternatively, the switch 515 may receivethe network traffic from a storage sled 704, such as a sled 704 thatincludes one or more data storage devices (e.g., physical storageresources 205-1), as indicated in block 1414. The switch 515 mayadditionally or alternatively receive the network traffic from anaccelerator sled 704, such as a sled 704 that includes one or moreco-processors, field programmable gate arrays (FPGAs) or otherspecialized hardware for performing a computation (e.g., physicalaccelerator resources 205-2), as indicated in block 1416. Additionallyor alternatively, the switch 515 may receive the network traffic from amemory sled 704 such as a sled 704 that includes one or more memorydevices (e.g., physical memory resources 205-3), as indicated in block1418. The switch 515 may additionally or alternatively receive thenetwork traffic from another switch, as indicated in block 1420. Indoing so, the switch 515 may receive the network traffic from a leafswitch (e.g., a leaf switch 530 of FIG. 5) in a leaf-spine architecture,as indicated in block 1422. Alternatively, the switch 515 may receivethe network traffic from a spine switch (e.g., a spine switch 520 ofFIG. 5) in the leaf-spine architecture, as indicated in block 1424.

Still referring to FIG. 14, after receiving the network traffic, themethod 1400 advances to block 1426 in which the switch 515 determinesthe link layer protocol of the network traffic, as indicated in block1426. In doing so, the switch 515 may determine whether the networktraffic includes Ethernet protocol traffic or HPC network traffic, asindicated in block 1428. Additionally or alternatively, the switch 515may determine whether the network traffic includes traffic of adifferent network protocol (e.g., other than Ethernet or HPC traffic),as indicated in block 1430. As discussed above, the switch 515 maydetermine the type of network traffic by identifying aspects of theframe, such as a size of the frame, fields within the frame, and/or oneor more codes included in the frame and comparing the aspects to theprotocol data 1304 to determine whether a matching protocol (i.e., a setof reference aspects that match the identified aspects) is includedtherein. After determining the link layer protocol, the method 1400advances to block 1432 of FIG. 15 in which the switch 515 forwards thenetwork traffic.

Referring now to FIG. 15, in block 1432, the switch 515 forwards thenetwork traffic according to the link layer protocol (e.g., as afunction of the corresponding rules defined in the protocol data 1304).In doing so, in the illustrative embodiment, the switch 515 determinesthe destination address as a function of the link layer protocol, asindicated in block 1434. In doing so, in the illustrative embodiment,the switch 515 identifies the address of the device to which each frameof network traffic is to be forwarded, by extracting the data from theframe pursuant to the identified communication protocol (e.g., byextracting data from a particular location within the frame as specifiedin the protocol data 1304) and reading the address data 1306 to matchthe identified address to a physical port of the NICS 1210 where thedevice matching the identified address is connected. In block 1436, inthe illustrative embodiment, the switch 515 forwards the network trafficto the destination address. In the illustrative embodiment, inforwarding the network traffic, the switch 515, transmits the frame ofthe network data through the physical port matched above. Further, inthe illustrative embodiment, the switch 515 forwards the network trafficthrough an optical connection (e.g., optical fiber), as indicated inblock 1438. Moreover, in the illustrative embodiment, in forwarding thenetwork traffic, the switch 515 forwards the network traffic through aconnection having a portion (e.g., one quarter or other portion) of thetotal bandwidth of a link (e.g., a 50 gigabit per second connection of a200 gigabit per second link, a 100 gigabit per second connection of a400 gigabit per second link, a 200 gigabit per second connection of an800 gigabit per second link, etc.), as indicated in block 1440.

Still referring to FIG. 15, as indicated in block 1442, in forwardingthe network traffic, the switch 515 may forward the network traffic to asled 704. In doing so, the switch 515 may forward the network traffic toa compute sled 704 as indicated in block 1444. Alternatively, the switch515 may forward the network traffic to a storage sled 704, as indicatedin block 1446. As indicated in block 1448, the switch 515 may forwardthe network traffic to an accelerator sled 704. Alternatively, asindicated in block 1450, the switch 515 may forward the network trafficto a memory sled 704. As indicated in block 1452, the switch 515 mayalternatively forward the network traffic to another switch 515, such asto a leaf switch 530 as indicated in block 1454 or to a spine switch, asindicated in block 1456. After forwarding the network traffic, themethod 1400 loops back to block 1402 of FIG. 14 to determine whether tocontinue switching the network traffic.

EXAMPLES

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 includes a network switch comprising one or more processors;communication circuitry coupled to the one or more processors, whereinthe communication circuitry is to assist the one or more processors toswitch network traffic of multiple link layer protocols; one or morememory devices having stored therein a plurality of instructions that,when executed, cause the network switch to receive, with thecommunication circuitry through an optical connection, network trafficto be forwarded; determine a link layer protocol of the received networktraffic, wherein the received network traffic is formatted according toone of the multiple link layer protocols; and forward the networktraffic as a function of the determined link layer protocol to adestination network device.

Example 2 includes the subject matter of Example 1, and wherein toreceive the network traffic comprises to receive network traffic throughan optical connection that provides one fourth of a total bandwidth of alink.

Example 3 includes the subject matter of any of Examples 1 and 2, andwherein to receive the network traffic comprises to receive the networktraffic from a sled coupled to the optical connection.

Example 4 includes the subject matter of any of Examples 1-3, andwherein to receive the network traffic from a sled comprises to receivethe network traffic from at least one of a compute sled that includesone or more processors, a storage sled that includes one or more datastorage devices, an accelerator sled that includes one or moreco-processors or field programmable gate arrays, or a memory sled thatincludes one or more memory devices.

Example 5 includes the subject matter of any of Examples 1-4, andwherein to receive the network traffic comprises to receive the networktraffic from another network switch.

Example 6 includes the subject matter of any of Examples 1-5, andwherein to receive the network traffic from another network switchcomprises to receive the network traffic from a leaf switch or a spineswitch in a leaf-spine network architecture.

Example 7 includes the subject matter of any of Examples 1-6, andwherein the plurality of instructions further cause the network switchto forward traffic of two or more different link layer protocols.

Example 8 includes the subject matter of any of Examples 1-7, andwherein to determine a link layer protocol of the received networktraffic comprises to determine whether the link layer protocol is anEthernet protocol, a high performance computing (HPC) protocol, or otherspecialized communications protocol.

Example 9 includes the subject matter of any of Examples 1-8, andwherein to forward the network traffic as a function of the determinedlink layer protocol comprises to determine a destination address of thenetwork traffic as a function of the determined link layer protocol.

Example 10 includes the subject matter of any of Examples 1-9, andwherein to forward the network traffic comprises to forward, with thecommunication circuitry, the network traffic through another opticalconnection to one of a sled or another network switch.

Example 11 includes the subject matter of any of Examples 1-10, andwherein to forward the network traffic comprises to forward the networktraffic to one of a leaf switch or a spine switch in a leaf-spinenetwork architecture.

Example 12 includes the subject matter of any of Examples 1-11, andwherein to forward the network traffic comprises to forward the networktraffic through an optical connection that provides one fourth of atotal bandwidth of a link.

Example 13 includes the subject matter of any of Examples 1-12, andwherein to forward the network traffic comprises to forward the networktraffic to at least one of a compute sled that includes one or moreprocessors, a storage sled that includes one or more data storagedevices, an accelerator sled that includes one or more co-processors orfield programmable gate arrays, or a memory sled that includes one ormore memory devices.

Example 14 includes a method for switching network traffic comprisingreceiving, by a network switch through an optical connection, networktraffic to be forwarded; determining, by the network switch, a linklayer protocol of the received network traffic, wherein the determinedlink layer protocol is one of multiple link layer protocols supported bythe switch; and forwarding, by the network switch, the network trafficas a function of the determined link layer protocol to a destinationnetwork device.

Example 15 includes the subject matter of Example 14, and whereinreceiving the network traffic comprises receiving network trafficthrough an optical connection that provides one fourth of a totalbandwidth of a link.

Example 16 includes the subject matter of any of Examples 14 and 15, andwherein receiving the network traffic comprises receiving the networktraffic from a sled coupled to the optical connection.

Example 17 includes the subject matter of any of Examples 14-16, andwherein receiving the network traffic from a sled comprises receivingthe network traffic from at least one of a compute sled that includesone or more processors, a storage sled that includes one or more datastorage devices, an accelerator sled that includes one or moreco-processors or field programmable gate arrays, or a memory sled thatincludes one or more memory devices.

Example 18 includes the subject matter of any of Examples 14-17, andwherein receiving the network traffic comprises receiving the networktraffic from another network switch.

Example 19 includes the subject matter of any of Examples 14-18, andwherein receiving the network traffic from another network switchcomprises to receiving the network traffic from a leaf switch or a spineswitch in a leaf-spine network architecture.

Example 20 includes the subject matter of any of Examples 14-19, andfurther including forwarding, by the network switch, network traffic oftwo or more different link layer protocols.

Example 21 includes the subject matter of any of Examples 14-20, andwherein determining a link layer protocol of the received networktraffic comprises determining whether the link layer protocol is anEthernet protocol, a high performance computing (HPC) protocol, or otherspecialized communications protocol.

Example 22 includes the subject matter of any of Examples 14-21, andwherein forwarding the network traffic as a function of the determinedlink layer protocol comprises determining a destination address of thenetwork traffic as a function of the determined link layer protocol.

Example 23 includes the subject matter of any of Examples 14-22, andwherein forwarding the network traffic comprises forwarding the networktraffic through another optical connection to one of a sled or anothernetwork switch.

Example 24 includes the subject matter of any of Examples 14-23, andwherein forwarding the network traffic comprises forwarding the networktraffic to one of a leaf switch or a spine switch in a leaf-spinenetwork architecture.

Example 25 includes the subject matter of any of Examples 14-24, andwherein forwarding the network traffic comprises forwarding the networktraffic through an optical connection that provides one fourth of atotal bandwidth of a link.

Example 26 includes the subject matter of any of Examples 14-25, andwherein forwarding the network traffic comprises forwarding the networktraffic to at least one of a compute sled that includes one or moreprocessors, a storage sled that includes one or more data storagedevices, an accelerator sled that includes one or more co-processors orfield programmable gate arrays, or a memory sled that includes one ormore memory devices.

Example 27 includes one or more machine-readable storage mediacomprising a plurality of instructions stored thereon that in responseto being executed, cause a network switch to perform the method of anyof Examples 14-26.

Example 28 includes a network switch comprising one or more processors;communication circuitry coupled to the one or more processors; one ormore memory devices having stored therein a plurality of instructionsthat, when executed, cause the network switch to perform the method ofany of Examples 14-26.

Example 29 includes a network switch comprising means for performing themethod of any of Examples 14-26.

Example 30 includes a network switch comprising network communicatorcircuitry to receive, through an optical connection, network traffic tobe forwarded; protocol determiner circuitry to determine a link layerprotocol of the received network traffic, wherein the received networktraffic is formatted according to one of multiple link layer protocols;and network traffic switcher circuitry to forward the network traffic asa function of the determined link layer protocol to a destinationnetwork device.

Example 31 includes the subject matter of Example 30, and wherein toreceive the network traffic comprises to receive network traffic throughan optical connection that provides one fourth of a total bandwidth of alink.

Example 32 includes the subject matter of any of Examples 30 and 31, andwherein to receive the network traffic comprises to receive the networktraffic from a sled coupled to the optical connection.

Example 33 includes the subject matter of any of Examples 30-32, andwherein to receive the network traffic from a sled comprises to receivethe network traffic from at least one of a compute sled that includesone or more processors, a storage sled that includes one or more datastorage devices, an accelerator sled that includes one or moreco-processors or field programmable gate arrays, or a memory sled thatincludes one or more memory devices.

Example 34 includes the subject matter of any of Examples 30-33, andwherein to receive the network traffic comprises to receive the networktraffic from another network switch.

Example 35 includes the subject matter of any of Examples 30-34, andwherein to receive the network traffic from another network switchcomprises to receive the network traffic from a leaf switch or a spineswitch in a leaf-spine network architecture.

Example 36 includes the subject matter of any of Examples 30-35, andwherein the network traffic switcher circuitry is further to forwardtraffic of two or more different link layer protocols.

Example 37 includes the subject matter of any of Examples 30-36, andwherein to determine a link layer protocol of the received networktraffic comprises to determine whether the link layer protocol is anEthernet protocol, a high performance computing (HPC) protocol, or otherspecialized communications protocol.

Example 38 includes the subject matter of any of Examples 30-37, andwherein to forward the network traffic as a function of the determinedlink layer protocol comprises to determine a destination address of thenetwork traffic as a function of the determined link layer protocol.

Example 39 includes the subject matter of any of Examples 30-38, andwherein to forward the network traffic comprises to forward the networktraffic through another optical connection to one of a sled or anothernetwork switch.

Example 40 includes the subject matter of any of Examples 30-39, andwherein to forward the network traffic comprises to forward the networktraffic to one of a leaf switch or a spine switch in a leaf-spinenetwork architecture.

Example 41 includes the subject matter of any of Examples 30-40, andwherein to forward the network traffic comprises to forward the networktraffic through an optical connection that provides one fourth of atotal bandwidth of a link.

Example 42 includes the subject matter of any of Examples 30-41, andwherein to forward the network traffic comprises to forward the networktraffic to at least one of a compute sled that includes one or moreprocessors, a storage sled that includes one or more data storagedevices, an accelerator sled that includes one or more co-processors orfield programmable gate arrays, or a memory sled that includes one ormore memory devices.

Example 43 includes a network switch comprising circuitry for receiving,through an optical connection, network traffic to be forwarded; meansfor determining a link layer protocol of the received network traffic,wherein the received network traffic is formatted according to one ofone of multiple link layer protocols; and means for forwarding thenetwork traffic as a function of the determined link layer protocol to adestination network device.

Example 44 includes the subject matter of Example 43, and wherein thecircuitry for receiving the network traffic comprises circuitry forreceiving network traffic through an optical connection that providesone fourth of a total bandwidth of a link.

Example 45 includes the subject matter of any of Examples 43 and 44, andwherein the circuitry for receiving the network traffic comprisescircuitry for receiving the network traffic from a sled coupled to theoptical connection.

Example 46 includes the subject matter of any of Examples 43-45, andwherein the circuitry for receiving the network traffic from a sledcomprises circuitry for receiving the network traffic from at least oneof a compute sled that includes one or more processors, a storage sledthat includes one or more data storage devices, an accelerator sled thatincludes one or more co-processors or field programmable gate arrays, ora memory sled that includes one or more memory devices.

Example 47 includes the subject matter of any of Examples 43-46, andwherein the circuitry for receiving the network traffic comprisescircuitry for receiving the network traffic from another network switch.

Example 48 includes the subject matter of any of Examples 43-47, andwherein the circuitry for receiving the network traffic from anothernetwork switch comprises circuitry for receiving the network trafficfrom a leaf switch or a spine switch in a leaf-spine networkarchitecture.

Example 49 includes the subject matter of any of Examples 43-48, andfurther including means for forwarding network traffic of two or moredifferent link layer protocols.

Example 50 includes the subject matter of any of Examples 43-49, andwherein the means for determining a link layer protocol of the receivednetwork traffic comprises means for determining whether the link layerprotocol is an Ethernet protocol, a high performance computing (HPC)protocol, or other specialized communications protocol.

Example 51 includes the subject matter of any of Examples 43-50, andwherein the means for forwarding the network traffic as a function ofthe determined link layer protocol comprises means for determining adestination address of the network traffic as a function of thedetermined link layer protocol.

Example 52 includes the subject matter of any of Examples 43-51, andwherein the means for forwarding the network traffic comprises means forforwarding the network traffic through another optical connection to oneof a sled or another network switch.

Example 53 includes the subject matter of any of Examples 43-52, andwherein the means for forwarding the network traffic comprises means forforwarding the network traffic to one of a leaf switch or a spine switchin a leaf-spine network architecture.

Example 54 includes the subject matter of any of Examples 43-53, andwherein the means for forwarding the network traffic comprises means forforwarding the network traffic through an optical connection thatprovides one fourth of a total bandwidth of a link.

Example 55 includes the subject matter of any of Examples 43-54, andwherein the means for forwarding the network traffic comprises means forforwarding the network traffic to at least one of a compute sled thatincludes one or more processors, a storage sled that includes one ormore data storage devices, an accelerator sled that includes one or moreco-processors or field programmable gate arrays, or a memory sled thatincludes one or more memory devices.

Example 56 includes a data center comprising a plurality of racks eachcontaining a plurality of sleds; one or more multi mode optical switchescoupled to the sleds by an optical connection, wherein the racks do notcomprise a top-of-rack switch.

Example 57 includes the subject matter of Example 56, and wherein theone or more switches comprise multiple switches and each switch isconnected to each of the sleds by an upstream optical connection and adownstream optical connection.

Example 58 includes the subject matter of any of Examples 56 and 57, andwherein each optical connection provides one fourth of a total bandwidthof a switch link.

Example 59 includes the subject matter of any of Examples 56-58, andwherein a first subgroup of the sleds is to communicate with a firstlink layer protocol; and a second subgroup of the sleds is tocommunicate with a second link layer protocol that is different than thefirst link layer protocol; and the one or more switches are toconcurrently switch network traffic among the plurality of sleds with atleast the first link layer protocol and the second link layer protocol.

Example 60 includes the subject matter of any of Examples 56-59, andwherein the first link layer protocol is a non-Ethernet protocol and thesecond link layer protocol is an Ethernet protocol.

Example 61 includes the subject matter of any of Examples 56-60, andwherein the one or more switches comprise a plurality of switchesarranged in a leaf-spine architecture.

Example 62 includes the subject matter of any of Examples 56-61, andwherein each sled comprises one or more physical resources, the one ormore switches comprise four switches, each sled is coupled to each ofthe four switches, and each physical resource of each sled is coupled tothe four switches.

Example 63 includes the subject matter of any of Examples 56-62, andwherein the one or more switches are arranged in a two-layer switcharchitecture.

Example 64 includes the subject matter of any of Examples 56-63, andwherein at least one of the switches is a spine switch connected to eachsled at one fourth of a total switch link bandwidth.

Example 65 includes the subject matter of any of Examples 56-64, andwherein the spine switch is additionally connected to one or more otherconnections at the total switch link bandwidth.

Example 66 includes the subject matter of any of Examples 56-65, andwherein the at least one spine switch is a plurality of spine switches.

Example 67 includes a data center comprising a layer of spine switches;a plurality of racks, wherein each rack includes multiple sleds, andwherein each sled is to connect multiple other sleds with the layer ofspine switches.

Example 68 includes a data center comprising a two-layer switch systemthat includes a layer of spine switches; and a layer of leaf switchesconnected to the layer of spine switches; and a plurality of racks,wherein each rack includes multiple sleds, and wherein each sled is toconnect multiple other sleds with the two-layer switch system.

1-20. (canceled)
 21. A system-on-chip (SoC) network switch integrated circuit (IC) for use in forwarding network traffic that is in accordance with multiple different link layer communication protocols, the network traffic to be forwarded via a physical port associated with the SoC network switch IC to an optical communication channel and thence to a destination network device, the SoC network switch IC comprising: network communication circuitry for use, when the SoC network switch IC is in operation, in (1) receiving multiprotocol inbound network communication to the SoC network switch IC and (2) transmitting multiprotocol outbound network communication from the SoC network switch IC; network traffic switching circuitry for use in outbound network communication forwarding address determination; wherein, when the SoC network switch IC is in the operation: based upon frame data accessed by the SoC network switch IC as a function of one or more of the multiple different link layer communication protocols determined by the SoC network switch IC to correspond to the network traffic, the SoC network switch IC is to identify (1) a forwarding address of the destination network device to which the network traffic is to be forwarded by the SoC network switch IC that corresponds to the physical port, (2) a communication protocol-related code, and (3) a forwarding rule; the forwarding address, the code, and the forwarding rule are to be used by the SoC network switch IC to determine forwarding by the SoC network switch IC of the network traffic; the network traffic is formatted in accordance with the one or more of the multiple different link layer communication protocols; the network communication circuitry is configurable to transmit the network traffic via the physical port; the optical communication channel is to communicate a portion of a total bandwidth of a communication link; the portion is configurable to be a quarter of the total bandwidth; the SoC network switch IC is configurable to provide telemetry information related, at least in part, to the SoC network switch IC for use in: cloud service quality of service management; failure condition detection and prevention; and software defined infrastructure management.
 22. The SoC network switch IC of claim 21, wherein: the frame data is comprised in the network traffic; and the frame data comprises the communication protocol-related code.
 23. The SoC network switch IC of claim 21, wherein: the SoC network switch IC is configurable for use with a circuit board that is for use in a rack; and the SoC network switch IC is configurable to be coupled via the physical port to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.
 24. The SoC network switch IC of claim 23, wherein: the optical switch infrastructure comprises one or more of: an optical fabric; a leaf switch; and a spine switch.
 25. The SoC network switch IC of claim 24, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol.
 26. The SoC network switch IC of claim 25, wherein: the another, different link layer protocol comprises an OmniPath protocol.
 27. At least one machine-readable storage medium storing instructions for execution by a system-on-chip (SoC) network switch integrated circuit (IC), the SoC network switch IC being for use, when the SoC network switch IC is in operation, in forwarding network traffic that is in accordance with multiple different link layer communication protocols, the network traffic to be forwarded via a physical port associated with the SoC network switch IC to an optical communication channel and thence to a destination network device, the instructions when executed by the SoC network switch IC resulting in the SoC network switch being configured to perform operations comprising: using network communication circuitry of the SoC network switch IC to receive multiprotocol inbound network communication to the SoC network switch IC; using the network communication circuitry to transmit multiprotocol outbound network communication from the SoC network switch IC; using network traffic switching circuitry of the SoC network switch IC in outbound network communication forwarding address determination; and identifying, based upon frame data accessed by the SoC network switch IC as a function of one or more of the multiple different link layer communication protocols determined by the SoC network switch IC to correspond to the network traffic, (1) a forwarding address of the destination network device to which the network traffic is to be forwarded by the SoC network switch IC that corresponds to the physical port, (2) a communication protocol-related code, and (3) a forwarding rule; and wherein, when the SoC network switch IC is in the operation: the forwarding address, the code, and the forwarding rule are to be used by the SoC network switch IC to determine forwarding by the SoC network switch IC of the network traffic; the network traffic is formatted in accordance with the one or more of the multiple different link layer communication protocols; the network communication circuitry is configurable to transmit the network traffic via the physical port; the optical communication channel is to communicate a portion of a total bandwidth of a communication link; the portion is configurable to be a quarter of the total bandwidth; the SoC network switch IC is configurable to provide telemetry information related, at least in part, to the SoC network switch IC for use in: cloud service quality of service management; failure condition detection and prevention; and software defined infrastructure management.
 28. The at least one machine-readable storage medium of claim 27, wherein: the frame data is comprised in the network traffic; and the frame data comprises the communication protocol-related code.
 29. The at least one machine-readable storage medium of claim 27, wherein: the SoC network switch IC is configurable for use with a circuit board that is for use in a rack; and the SoC network switch IC is configurable to be coupled via the physical port to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.
 30. The at least one machine-readable storage medium of claim 29, wherein: the optical switch infrastructure comprises one or more of: an optical fabric; a leaf switch; and a spine switch.
 31. The at least one machine-readable storage medium of claim 30, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol.
 32. The at least one machine-readable storage medium of claim 31, wherein: the another, different link layer protocol comprises an OmniPath protocol.
 33. A method implemented, at least in part, by a system-on-chip (SoC) network switch integrated circuit (IC), the SoC network switch IC being for use, when the SoC network switch IC is in operation, in forwarding network traffic that is in accordance with multiple different link layer communication protocols, the network traffic to be forwarded via a physical port associated with the SoC network switch IC to an optical communication channel and thence to a destination network device, the method comprising: using network communication circuitry of the SoC network switch IC to receive multiprotocol inbound network communication to the SoC network switch IC; using the network communication circuitry to transmit multiprotocol outbound network communication from the SoC network switch IC; using network traffic switching circuitry of the SoC network switch IC in outbound network communication forwarding address determination; and identifying, based upon frame data accessed by the SoC network switch IC as a function of one or more of the multiple different link layer communication protocols determined by the SoC network switch IC to correspond to the network traffic, (1) a forwarding address of the destination network device to which the network traffic is to be forwarded by the SoC network switch IC that corresponds to the physical port, (2) a communication protocol-related code, and (3) a forwarding rule; and wherein, when the SoC network switch IC is in the operation: the forwarding address, the code, and the forwarding rule are to be used by the SoC network switch IC to determine forwarding by the SoC network switch IC of the network traffic; the network traffic is formatted in accordance with the one or more of the multiple different link layer communication protocols; the network communication circuitry is configurable to transmit the network traffic via the physical port; the optical communication channel is to communicate a portion of a total bandwidth of a communication link; the portion is configurable to be a quarter of the total bandwidth; the SoC network switch IC is configurable to provide telemetry information related, at least in part, to the SoC network switch IC for use in: cloud service quality of service management; failure condition detection and prevention; and software defined infrastructure management.
 34. The method of claim 33, wherein: the frame data is comprised in the network traffic; and the frame data comprises the communication protocol-related code.
 35. The method of claim 33, wherein: the SoC network switch IC is configurable for use with a circuit board that is for use in a rack; and the SoC network switch IC is configurable to be coupled via the physical port to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.
 36. The method of claim 35, wherein: the optical switch infrastructure comprises one or more of: an optical fabric; a leaf switch; and a spine switch.
 37. The method of claim 36, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol.
 38. The method of claim 37, wherein: the another, different link layer protocol comprises an OmniPath protocol. 